Home
Modeling software deployment
Modeling software deployment in HCL Launch includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
Statuses
Create and apply statuses to track component inventory states or to track component versions in environments and resources.
Adding snapshot statuses
Manage snapshot statuses through the snapshot options interface.

Modeling software deployment
Modeling software deployment in HCL Launch includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
- Components
  Components represent deployable items along with user-defined processes that operate on them, usually by deploying them.
- Resources
  A resource is a logical deployment target that typically resolves to an agent and a user-defined construct that is based on the architectural model of HCL Launch.
- Applications
  Applications are responsible for bringing together all the components that must be deployed together.
- Application environments
  An environment is a user-defined collection of resources that hosts an application.
- Application templates
  With an application template, you can save and reuse a collection of resources, environments, processes, and tagged components or component templates to create a standardized application.
- Application processes
  Application processes, like component processes, are created with the process editor. You use application processes to deploy or to roll back components.
- Application blueprints
  An application blueprint maps application components to a resource template. When you create an environment or provision one from the cloud, you can use the blueprint as a model.
- Snapshots
  A snapshot is a collection of specific versions of components and processes. Typically, a snapshot represents a set of component versions that are known to work together. In most cases, snapshots include all of the components in an application.
- Creating manual application tasks
  A manual application task interrupts an application process until manual intervention is done. To create a manual task, add a manual step to an application process and select a notification template.
- Approval process
  You can add approval requirements to deployments. Deployments with approvals cannot be completed until all approvers respond. Approvers can respond to requests on the Work Items tab, or by email.
- Inventories
  You use different inventories to track installed components and properties in HCL Launch elements.
- Processes
  Processes are automated tasks that run on agents.
- Statuses
  Create and apply statuses to track component inventory states or to track component versions in environments and resources.
  - Creating statuses
    Define component version, snapshot, and inventory statuses on the Statuses tab.
  - Adding version statuses
    Manage component version statuses through the version options interface.
  - Adding snapshot statuses
    Manage snapshot statuses through the snapshot options interface.
- Properties
  Properties are variables that store information about many different elements, including components, environments, processes, and applications. You can also set global properties for the system.
- Tags
  A tag is a user-defined, shared, short label that you use to classify, view, and conduct operations on objects such as applications, components, agents, and resources.
- Webhooks
  Using the webhooks, you can send text-based responses to users in messaging platform such as MS Teams and Slack when a specific event occurs during deployment process.
- Secret Stores
  Allows HCL Launch to retrieve credentials of individual servers from the Vault and authenticates a plug-in step in the deployment process.

Adding snapshot statuses

Manage snapshot statuses through the snapshot options interface.

About this task

You add a status to a snapshot to provide information about the snapshot deployment status. If a snapshot deployment fails, you might apply a Failed status to them. When a snapshot is deployed, you might set the status to Active.

Procedure

Click Applications > selected application.
To select the snapshot, click Snapshots > selected snapshot.
Click Add Status.
The Add a status window is displayed.
Select a status from the list, and click Save.

What to do next

You can now create snapshot gates using the snapshot statuses.